home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Tools (InfoMagic)
/
Internet Tools.iso
/
dos_win
/
winsock
/
hacklist
/
94-04.Z
/
94-04
/
000006_cornell@syl.dl.nec.com_Wed Apr 6 10:13:08 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-04-30
|
14KB
Received: from telemann.inoc.dl.nec.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA08027; Wed, 6 Apr 1994 16:13:29 -0400
Received: by telemann.inoc.dl.nec.com (4.1/YDL1.9-920831.09)
id AA25392(telemann.inoc.dl.nec.com); Wed, 6 Apr 94 15:13:14 CDT
Received: by texas.syl.dl.nec.com (8.6.4/YDL1.9-930614.17)
id PAA28068(texas.syl.dl.nec.com); Wed, 6 Apr 1994 15:13:12 -0500
Received: by michigan.syl.dl.nec.com (4.1/YDL1.9-920708.13)
id AA08128(michigan.syl.dl.nec.com); Wed, 6 Apr 94 15:13:09 CDT
From: cornell@syl.dl.nec.com (Cornell Kinderknecht)
Message-Id: <9404062013.AA08128@michigan.syl.dl.nec.com>
Subject: PC SOCKS Pack - PC Winsock clients behind firewall
To: winsock-hackers@sunsite.unc.edu
Date: Wed, 6 Apr 1994 15:13:08 -0500 (CDT)
Cc: ylee@syl.dl.nec.com (Ying-Da Lee),
cornell@syl.dl.nec.com (Cornell Kinderknecht)
X-Mailer: ELM [version 2.4 PL23beta]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 9532
Announcing the availability of the "PC SOCKS Pack" Version 1.01...
The "PC SOCKS Pack" is a collection of Windows network applications
that are Winsock 1.1 compliant that have been modified to be SOCKS
compliant. They can be run on PCs sitting behind a firewall that have
access to a SOCKS 4.0 or above server.
The "PC SOCKS Pack" is intended to be dynamic--adding more SOCKSified
PC network applications as they become available. Right now it's
pretty small and only contains three clients which I've converted.
We'd be happy to convert more Winsock compliant applications if source
is made available (hint hint).
The applications are:
FTP-s: This is very nice and is based on John A. Jounod's
WS_FTP version 93.12.05. Works pretty slick.
FINGER-s: This is based on Lee Murach's Finger 3.1. Pretty
self-explanatory and easy to use.
TELNET-s: This is real clunky (the SOCKS stuff works great
however) and has some bugs. It seems to work OK for
most sites that I've tried to connect to but it's
not too graceful about timed out connections and
other out of the ordinary things. It's based on the
NCSA unsupported beta 3 Wintel.
Anyone want to offer some nice, well-behaved Telnet
source to be converted over to SOCKS??????
You can get the "PC SOCKS Pack" via anonymous ftp from:
ftp.nec.com
in the directory
/pub/security/socks.cstc/PC_Socks_Pack
Grab the FILES file to see what's in there. All clients are archived
into one zip file.
NOTE: The zip files extract into multiple subdirectories so be
sure to supply the -d option to PKUNZIP.
The top directory of the release has information and detailed
instructions for configuring the PC for SOCKS and each subdirectory
has a SOCKSified application.
Questions and comments about the "PC SOCKS Pack" in general and the
SOCKS part of the individual applications can be directed to me. I'm
not much help with the original applications although I can probably
look at obvious bugs. I've left the user interface and workings of
the original applications pretty much untouched from the original.
Again, we're looking for source to other Winsock network applications
to convert over!!
At the end of this message, I'll include the README file from the
"PC SOCKS Pack" followed by a blurb describing SOCKS itself for those
unfamiliar with it.
--- Cornell
| Cornell Kinderknecht Email: cornell@syl.dl.nec.com |
| CSTC/CNAD |
| NEC Systems Lab./NEC USA Phone: 214-518-3509 |
| Irving, TX (Dallas) Fax: 214-518-3552 |
>>>>>>>>>> Start README file <<<<<<<<<<<<
============================
PC SOCKS Pack - Version 1.01
============================
File: README
Welcome to the PC SOCKS Pack. This is a collection of Windows Sockets
client applications that can be used from a PC sitting behind a
network firewall that has direct access to a proxy SOCKS server
running version 4.0 or above to reach hosts outside the firewall.
Presently, there are many packages available in the UNIX environment
that are SOCKS compliant and there seems to be a similar need in the
PC environment.
Currently, there are three applications included in the pack that I've
converted (SOCKSified) from other packages found on the net in source
form. I hope to add more to the collection. Can anyone point me to
the source for other packages? I'd like to find source for a Windows
Gopher client real fast.
The applications:
FINGER-s:
A finger application based on Lee Murach's Finger3.1.
WINTEL-s:
A telnet application based on NCSA's unsupported beta 3
telnet. This application is a bit buggy.
WS_FTP-s:
An ftp client based on John A. Junod's WS_FTP version
93.12.05.
-------------------
1.0 Where to get it
-------------------
If you're reading this file, chances are you already know where to get
it but just in case... The PC SOCKS Pack can be downloaded via
anonymous ftp from:
ftp.nec.com
in the directory:
/pub/security/socks.cstc/PC_Socks_Pack
Get the file "FILES" from that directory to see a description of
what's in the directory and what files you need to download.
----------------------
2.0 About this release
----------------------
The PC SOCKS Pack is distributed as a single ZIP file which extracts
into multiple directories (remember to use the -d option for PKUNZIP).
The top directory contains general information about the package and
instructions for configuring SOCKS on your system. Each subdirectory
contains an individual SOCKSified application with specific
installation instructions for the application along with files from
that package's original release.
The SOCKSification of each package only adds the capability to connect
to outside networks through a SOCKS server. The original user
interface and operation of each package have not been changed from the
original author's package.
I should mention that if you do not need the SOCKS capabilities, you
can still use the applications in this package by setting the SOCKS
configuration on your machine so that all connections are direct.
However, it's probably best to use the original un-modified
applications if you don't need SOCKS. In most cases, I've included a
copy of the original executable for convenience and testing purposes.
---------------------
3.0 Priliminary steps
---------------------
To see a description of all the files in this distribution, see the
"FILES" file in the top directory of this distribution.
If you need to know more about SOCKS itself, see the file "WHATSOCK"
in the top directory of this distribution.
There are some system and software requirements that you must meet in
order to use the PC SOCKS Pack. It is important that you read the
file "REQUIRES" and verify that all the requirements are met for your
system and network.
Please read and understand the individual copyrights and permissions
for each package. In the top directory, there is a file called
"COPYRGHT" that contains the notices and copyrights from all of the
applications included in this distribution. See the file "ACKNLGMT"
to see the credits for each application.
To see what system and software setups that this software has been
tested on, see the file "SYSTEMS". I'd like to add your system and
software setups to the list if you'd like to email me the information.
-------------------
4.0 Getting started
-------------------
To start installing the PC SOCKS Pack, please refer to the file
"INSTALL" in the top directory of this distribution.
----------------------
5.0 SOCKS Mailing List
----------------------
There is a mailing list for SOCKS maintained by the C&C Software
Technology Center at NEC Systems Lab. It's primarly a technical
discussion group concerning the ongoing development and nurturing of
the SOCKS protocol and related software. To join the SOCKS mailing
list, send email to:
majordomo@syl.dl.nec.com
with
subscribe socks your@email.address
as the first line of the message body.
-------------------------
6.0 PC SOCKS Pack Contact
-------------------------
The PC SOCKS Pack was organized and the applications in it were
converted for SOCKS compliance by:
Cornell Kinderknecht <cornell@syl.dl.nec.com>
C&C Software Technology Center (CSTC)
NEC Systems Laboratory
Permission to use, copy, modify, and distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies, and
that the name of NEC Systems Laboratory not be used in advertising or
publicity pertaining to distribution of the document or software
without specific, written prior permission.
THE SOFTWARE IS PROVIDED ``AS IS'' AND NEC SYSTEMS LABORATORY
DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
NEC SYSTEMS LABORATORY BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
>>>>>>>>>> Start What_Is_SOCKS.CSTC <<<<<<<<<<
What Is SOCKS.CSTC
SOCKS belongs to the type generally referred to as proxy servers.
Usually when a network firewall is set up to protect hosts inside
an organization from attacks that may come from outside through
the network, these inside hosts lose their IP-accessibility with
the outside world and thus can no longer use things like telnet,
ftp, gopher, WWW, etc. to access the vast resources available in
the Internet. Proxy servers with their clients restore these
functions to the hosts inside the firewall without breaching their
security requirements.
The original SOCKS was written by David Koblas <koblas@netcom.com>.
The CSTC releases have been mainly the results of work by Ying-Da Lee
<ylee@syl.dl.nec.com> of C&C Software Technology Center (CSTC), NEC
Systems Laboratory, with contributions by many others throughout the
world.
The current CSTC release is version 4.1. It is known to run on
SunOS 4.1.x, Irix 4.0.x, Ultrix 4.3, HP-UX 9.0x, AIX 3.2.x,
Interactive Systems Unix, Alpha OSF 1.3, Solaris 2.2, NetBSD 0.9,
UnixWare, and Linux 0.99pl13.
The SOCKS.CSTC release can be found via anonymous ftp to ftp.nec.com
in the directory /pub/security/socks.cstc. The file "FILES" in that
directory describes what is contained there.
From paul@atlas.dev.abccomp.oz.au Fri Apr 8 05:21:46 1994
Received: from usage.csd.unsw.OZ.AU by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA03216; Thu, 7 Apr 1994 20:08:28 -0400
Received: by usage.csd.unsw.OZ.AU id AA05255
(5.65c/IDA-1.4.4 for winsock-hackers%sunsite.unc.edu); Fri, 8 Apr 1994 10:08:46 +1000
Received: by atlas (4.1/1.35)
id AA23171; Fri, 8 Apr 94 10:21:47 EST
Message-Id: <9404080021.AA23171@atlas>
From: paul@atlas.abccomp.oz.au
Date: Fri, 8 Apr 1994 10:21:46 -0500
X-Mailer: Mail User's Shell (7.2.2 4/12/91)
To: winsock-hackers@sunsite.unc.edu
Subject: WSAENOBUFS error from WSAAsyncGetXXXByYYY
I've got a problem with my stack testing, and would like to
take another straw poll (results of the last one soon!)
The application is expecting all error returns from WSAAsyncGetXXXByYYY
routines to be returned along with the completion message.
Some conditions, however, are detectable at the time the call is made.
The one causing the trouble at the moment is WSAENOBUFS. If the application
calls WSAAsynGetHostByName with buf==NULL, I fail the call immediately,
instead of accepting the call then immediately posting a message with
WSAENOBUFS in LPARAM. Now failing the call immediately seems to be perfectly
valid from my reading of the spec - what do you all do/say/expect?
--
Paul Brooks |paul@abccomp.oz.au |Emerging Standard:
TurboSoft Pty Ltd |pwb@newt.phys.unsw.edu.au| one that has not yet
579 Harris St., Ultimo | | been superseded.
Sydney Australia 2007 |ph: +61 2 281 3155 |
From bruce@isi.FrontierTech.COM Fri Apr 8 02:45:21 1994
Received: from isi.FrontierTech.COM by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA13407; Fri, 8 Apr 1994 09:45:27 -0400
Received: from bruces.FrontierTech.COM by isi.FrontierTech.COM (5.65/1.40)
id AA05627; Fri, 8 Apr 94 08:45:31 -0500
X-Mailer: SuperTCP/NFS for Windows Version 4.00 (Mailer Version 1.02)
Message-Id: <2DA56E04-00000001@Bruces.FrontierTech.COM>
From: Bruce@isi.FrontierTech.COM
Date: Fri, 08 Apr 94 08:45:21 CST
Subject: Re: Curious behaviour from winsock
To: winsock-hackers@sunsite.unc.edu
Mime-Version: 1.0
Content-Type: Text/Plain; Charset=US-ASCII
icode@teleport.com (Mark Clouden) writes:
>When using non blocking sockets with lingering enabled (l_onoff=1,
>l_linger!=0), I call closesocket and get WSAEWOULDBLOCK back. Now great,
>I expected that, but where is my notification message when it does
>close?? Or actually, when will it close? - because according to my
>network monitor app the socket is still connected.
>
I don't know about the second problem (the connection not actually
closing), but I wouldn't expect you would get any more notifications on a
socket after you closesocket it, since the socket descriptor is then
invalidated. If you want full graceful shutdown and notifications along
the way, I would suggest shutting down for writing to close your end, and
reading 'til "end-of-file" to detect the other side's close.
****************************************
Bruce A Backman (Bruce@FrontierTech.COM)
Frontier Technologies Corporation
10201 North Port Washington Road
Mequon, WI 53092
****************************************